Add check for non-cellstr cell types #463
Merged
+5
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
One potential misconception about ragged array before may cause a type corruption on write. In the case of #462,
addRow
supports multi-ragged array appending behavior via use of cell arrays. This is not true for regular instantiation. Regular constructor instantiation is intended for purely raw data initialization.Users who wish to emulate the behavior in
addRow
should actually construct the vector index objects themselves if they wish to construct dyamic tables using the default constructor.In the case of MatNWB, cell arrays passed in this way must error, otherwise silent data corruption can occur.
How to test the behavior?
Should throw an error. Not write the file.
Checklist
fix #XX
whereXX
is the issue number?